<meta charset="utf-8">
(#) `load` used to dynamically load code

!!! WARNING: `load` used to dynamically load code
   This is a warning.

Id
:   `UnsafeDynamicallyLoadedCode`
Summary
:   `load` used to dynamically load code
Severity
:   Warning
Category
:   Security
Platform
:   Android
Vendor
:   Android Open Source Project
Feedback
:   https://issuetracker.google.com/issues/new?component=192708
Since
:   2.0.0 (April 2016)
Affects
:   Kotlin and Java files
Editing
:   This check runs on the fly in the IDE editor
Implementation
:   [Source Code](https://cs.android.com/android-studio/platform/tools/base/+/mirror-goog-studio-main:lint/libs/lint-checks/src/main/java/com/android/tools/lint/checks/UnsafeNativeCodeDetector.java)
Tests
:   [Source Code](https://cs.android.com/android-studio/platform/tools/base/+/mirror-goog-studio-main:lint/libs/lint-tests/src/test/java/com/android/tools/lint/checks/UnsafeNativeCodeDetectorTest.kt)

Dynamically loading code from locations other than the application's
library directory or the Android platform's built-in library directories
is dangerous, as there is an increased risk that the code could have
been tampered with. Applications should use `loadLibrary` when possible,
which provides increased assurance that libraries are loaded from one of
these safer locations. Application developers should use the features of
their development environment to place application native libraries into
the lib directory of their compiled APKs.

(##) Example

Here is an example of lint warnings produced by this check:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~text
src/test/pkg/Load.java:12:Warning: Dynamically loading code using load
is risky, please use loadLibrary instead when possible
[UnsafeDynamicallyLoadedCode]
    Runtime.getRuntime().load("/data/data/test.pkg/files/libhello.so");
    ------------------------------------------------------------------
src/test/pkg/Load.java:14:Warning: Dynamically loading code using load
is risky, please use loadLibrary instead when possible
[UnsafeDynamicallyLoadedCode]
    System.load("/data/data/test.pkg/files/libhello.so");
    ----------------------------------------------------
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Here is the source file referenced above:

`src/test/pkg/Load.java`:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~java linenumbers
package test.pkg;

import java.lang.NullPointerException;
import java.lang.Runtime;
import java.lang.SecurityException;
import java.lang.System;
import java.lang.UnsatisfiedLinkError;

public class Load {
    public static void foo() {
        try {
            Runtime.getRuntime().load("/data/data/test.pkg/files/libhello.so");
            Runtime.getRuntime().loadLibrary("hello"); // ok
            System.load("/data/data/test.pkg/files/libhello.so");
            System.loadLibrary("hello"); // ok
        } catch (SecurityException ignore) {
        } catch (UnsatisfiedLinkError ignore) {
        } catch (NullPointerException ignore) {
        }
    }
}
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

You can also visit the
[source code](https://cs.android.com/android-studio/platform/tools/base/+/mirror-goog-studio-main:lint/libs/lint-tests/src/test/java/com/android/tools/lint/checks/UnsafeNativeCodeDetectorTest.kt)
for the unit tests for this check to see additional scenarios.

(##) Suppressing

You can suppress false positives using one of the following mechanisms:

* Using a suppression annotation like this on the enclosing
  element:

  ```kt
  // Kotlin
  @Suppress("UnsafeDynamicallyLoadedCode")
  fun method() {
     load(...)
  }
  ```

  or

  ```java
  // Java
  @SuppressWarnings("UnsafeDynamicallyLoadedCode")
  void method() {
     load(...);
  }
  ```

* Using a suppression comment like this on the line above:

  ```kt
  //noinspection UnsafeDynamicallyLoadedCode
  problematicStatement()
  ```

* Using a special `lint.xml` file in the source tree which turns off
  the check in that folder and any sub folder. A simple file might look
  like this:
  ```xml
  &lt;?xml version="1.0" encoding="UTF-8"?&gt;
  &lt;lint&gt;
      &lt;issue id="UnsafeDynamicallyLoadedCode" severity="ignore" /&gt;
  &lt;/lint&gt;
  ```
  Instead of `ignore` you can also change the severity here, for
  example from `error` to `warning`. You can find additional
  documentation on how to filter issues by path, regular expression and
  so on
  [here](https://googlesamples.github.io/android-custom-lint-rules/usage/lintxml.md.html).

* In Gradle projects, using the DSL syntax to configure lint. For
  example, you can use something like
  ```gradle
  lintOptions {
      disable 'UnsafeDynamicallyLoadedCode'
  }
  ```
  In Android projects this should be nested inside an `android { }`
  block.

* For manual invocations of `lint`, using the `--ignore` flag:
  ```
  $ lint --ignore UnsafeDynamicallyLoadedCode ...`
  ```

* Last, but not least, using baselines, as discussed
  [here](https://googlesamples.github.io/android-custom-lint-rules/usage/baselines.md.html).

<!-- Markdeep: --><style class="fallback">body{visibility:hidden;white-space:pre;font-family:monospace}</style><script src="markdeep.min.js" charset="utf-8"></script><script src="https://morgan3d.github.io/markdeep/latest/markdeep.min.js" charset="utf-8"></script><script>window.alreadyProcessedMarkdeep||(document.body.style.visibility="visible")</script>